home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20010921-20020314
/
000269_fdc@columbia.edu_Sun Dec 30 11:58:36 EST 2001.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
2KB
|
46 lines
Article: 13099 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit-95 on Win98 8E2 Problems
Date: 30 Dec 2001 11:57:02 -0500
Organization: Columbia University
Lines: 29
Message-ID: <a0nh0u$o7u$1@watsol.cc.columbia.edu>
References: <jsfu2u0g7b935fma82b50t726epg6i62os@4ax.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1009731423 3330 128.59.39.139 (30 Dec 2001 16:57:03 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 30 Dec 2001 16:57:03 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13099
In article <jsfu2u0g7b935fma82b50t726epg6i62os@4ax.com>,
Ron Heiby <heiby_u@falkor.chi.il.us> wrote:
: I struggled for a while to figure out how to send 8 data bits, even
: parity, and two stop bits. Using a pointer in an answer to a question
: posted here long ago, I found the documentation for doing this in the
: C-Kermit 7.0 Update Notes. From these, it appears that "SET SERIAL 8E2" is
: what I am looking for.
:
: However, doing this on my HP under Win98 (not SE) using K95 1.1.20 does
: not give me 8E2, even thought Kermit reports that setting when asked via
: "SHOW COMM".
:
: Instead (as shown by our scope), we appear to be getting 8N1.
:
: Attempting this using Hyperterminal does give us 8E2, so we know that the
: hardware and drivers are capable of this operation.
:
: I'd really like to be able to use Kermit's scripting capability to work
: with the odd-ball piece of hardware we're trying to talk with, but it is
: insisting on 8E2, which I have not been able to get working.
:
It's supposed to work and it does work on most kinds Unix.
If Hyperterminal can do it and Kermit 95 can't, it's either a bug (which
we can fix), or we're using the wrong API (which we can fix if the real
API for doing this can be determined -- as you know, many Windows APIs are
secret). We'll contact you offline when we have more information.
- Frank